| 1. | Immediate updating subscribers
即时更新订阅服务器 |
| 2. | Immediate updating subscriptions
即时更新订阅 |
| 3. | Governs how the triggers for immediate updating subscriptions execute calls at the publisher
参数控制即时更新订阅的触发器如何在发布服务器上执行调用。 |
| 4. | Subscriber , distributor , and publisher are connected most of the time for immediate updating subscriptions
大多数情况下，订阅服务器、分发服务器和发布服务器都是相互连接的（适用于立即更新订阅） 。 |
| 5. | Subscribers to oracle publications cannot use immediate updating or queued updating subscriptions , or be nodes in a peer - to - peer or bidirectional topology
Oracle发布的订阅服务器不能使用立即更新订阅或排队更新订阅，也不能作为对等或双向拓扑中的节点。 |
| 6. | If immediate updating or queued updating options are used with transactional replication , updates can be made at the subscriber , and with queued updating , conflicts might occur
如果事务性复制使用了立即更新或排队更新选项，更新可以在订阅服务器中进行，对于排队更新，可能会发生冲突。 |
| 7. | Because changes to the data must be made at the publisher when transactional replication is used without immediate updating or queued updating options , update conflicts are avoided
由于数据更改必须在发布服务器中进行（使用事务性复制时，无需指定立即更新或排队更新选项） ，从而避免了更新冲突。 |
| 8. | Therefore , oracle publishing does not support : publications with immediate updating or queued updating subscriptions ; or topologies in which publication tables also act as subscription tables , such as peer - to - peer and bidirectional replication
因此， oracle发布不支持以下功能：包含立即更新订阅或排队更新订阅的发布；或者其中发布表还作为订阅表的拓扑，例如，对等和双向复制。 |
| 9. | It does support queued updating using push subscriptions and immediate updating using push or pull subscriptions immediate updating requires that microsoft distributed transaction coordinator ms dtc be running on the same computer as the sse instance
Sse确实支持使用推送订阅进行排队更新，并且支持使用推送或请求订阅进行立即更新（立即更新需要在运行sse实例的计算机上运行microsoft分布式事务处理协调器( msdtc ) ） 。 |
